Hi all,My WD Mybookworld is not visible in "Network", and I can no longer accessall shared folders thereon as network drives.To note:1. I can ping the device, which has a fixed ip address on my network.2. I can access and configure the device throughits ip address on my network.3. Common workgroup name is assigned to all devices onthe network, including the Mybookworld and the pc running Windows 7.4. Noissue with other pcs running XP or Vista and my Imac in connecting to the Mybookworld.None of the troubleshooters provided by Windows7 helped. I have tried some of the fixes suggested out there, but nosuccess so far.Any help would be appreciated.Thanks in advanceGUYM45

Hi, Can you see any Windows XP computer from the Windows 7 beta computer? A possible cause is NetBIOS over TCP/IP. I suggest that you enable it. NetBIOS over TCP/IP If the issue persists, I suggest that you temporary disable the anti-virus and firewall on the computer. Hope it helps. Arthur Xie - MSFT

HI Authur and thanks for this, I did what you suggested, however still no good.I have even gone into adding the shared folders on the NAS drive into the credentials manager,tried with AV off, tried all the registry fixes, etc, etc and still no good. Seems to be a fairly widespread issue with NAs drives and Windows 7. Any other suggestions welcome... Cheers GUYM45

Hi GUYM45, Have you turned on Network Discovery on the Windows 7 computer? To do so, launch Network and sharing center, click related link in the left pane and you will see it. If the issue persists, this can be a compatibility issue. You may need to access the NAS with IP address. I also suggest that you contact WD support to see if this is a known issue for WD Mybookworld with Windows 7 beta. Arthur Xie - MSFT

Hi Arthur, I kept digging into the forum and here is the answer: I wrote the username and password used on theW7 machine and create them as auser on NAS drive and a local user on any other computerwhere you want to accessa shared folder (password should not be blank), giving them permissions on the shared resources. Once done, I rebooted and finally my NAs drive showed up. I can nowadd network drives at will and access all my shares from W7. Just a qualification: I had done an update of the firmwareof myrouter (D-link DIR655 Extreme N) the night before, so I don't know for sure whether this contributed to the solution or not. It could be the case as I can now see all computers on my network with the same workgroup from the W7 machine (using a "work" network setup on the W7 machine) Next step is to check for an update to the NAS firmware, to make sure all hardware is up to date. I think having all drivers, firmware, etc up to date is a must to make sure all works well in W7. Thanks for the assistance in any case. GUYM

Hi GUYM, Thank you for the shared answer. Arthur Xie - MSFT

I figure out that i just kept getting stalled or going in circles with this very issue. I started to give up completely but was able to come to a reasonable solution by exploring a related issue when I would run add device. First off log into your network device hard drive and go to the ADVANCED SETTINGS>USERS fill out your info accordingly. Now follow these steps. START>right click COMPUTER>MAP NETWORK DRIVE Follow example in the window. \\YOURDRIVESNAMEHERE\WHATEVERSHAREFOLDERYOUWANT Now to make sure this process has complete go to COMPUTER and under NETWORK LOCATION you will see your external. Hope I am able to help anyone who comes across this and encounters the horrid frustration I did.

I did close to what Whitney C did: Started mapping the WD MyBookWorld (Blue Ring) to X: and during this process using a specific WD-MBW user name (not one from my Win 2003 LAN). Worked well. Afterwards I cound use Add a Network Location in Windows 7. Taking a look into Win 7's credential manager I found an entry caused by this operation. A rather strange entry, though, being a mix of local domain name and WD-MBW user name. This is just one more incident in among many examples on how bad WD-MBW is designed.

I did close to what Whitney C did: Started mapping the WD MyBookWorld (Blue Ring) to X: and during this process using a specific WD-MBW user name (not one from my Win 2003 LAN). Worked well. Afterwards I cound use Add a Network Location in Windows 7. Taking a look into Win 7's credential manager I found an entry caused be this operation. A rather strange entry, though, being a mix of local domain name and WD-MBW user name. This is just one more incident in among many examples on how bad WD-MBW is designed.